System and method to access casualty health information in an emergency situation

ABSTRACT

A system, method, and computer program product for automatically identifying a casualty and matching an electronic health record (EHR) to the casualty. A casualty identification is determined by matching a presenting image of the casualty with one of a master image or a social media profile image of the casualty. A recognized patient messaging system (RPMS) is configured to query one or more electronic health records (EHR) service providers for the existence of an EHR corresponding the identified casualty and automatically communicate the existence of the EHR to the EMS provider. A blockchain trusted identification module (BTIM) is configured to establish a trust relationship between the EMS provider and the one or more EHR service providers to establish a trusted pathway for delivery of the casualty&#39;s EHR to the EMS provider. With the casualty&#39;s EHR emergency responders can provide better care for the casualty in an emergency.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 16/712,342, filed Dec. 12, 2019, which is a continuation-in-part application of U.S. Pat. No. 10,622,104 issued Apr. 14, 2020, which is a continuation in part application of U.S. Pat. No. 10,140,504, issued Nov. 27, 2019, each of which claim the benefit of priority to U.S. provisional application No. 62/241,232, filed Oct. 14, 2015, the contents of which are herein incorporated by reference.

BACKGROUND OF THE INVENTION

The present invention relates to electronic health records (EHR) and, more particularly, to the determining the existence of patient EHRs for use by emergency medical services (EMS) providers.

Over one million unconscious or non-communicative patients arrive in ERs every year in the United States. Unresponsive patients pose a major hurdle for emergency first responders in need of vital information in high-stakes situations. Access to electronic health records (EHR) provides first responders with medical backgrounds, emergency contact information, and medication histories, all of which are crucial in emergency treatment. However, when the patient is unresponsive it becomes difficult or impossible to locate and obtain protected health information, or even positively identify the patient being treated.

At present, a modern solution does not exist that allow first responders to determine the existence of a patient EHR, quickly and securely obtain protected information from EHR providers when patients are unresponsive, disoriented, or poorly versed in their medical background. Current means for obtaining this information involve slow investigation and communication with a disjoint medical record network, use of expensive and invasive biometrics, or analog tools like alert bracelets.

As of 1996, the Health Insurance Portability and Accountability Act (HIPAA) established national standards for the transaction of EHRs^(i). Patients' HIPAA-protected data includes vital medical records first responders need access to at the site of emergency treatment, so a key healthcare demand entails quickly transmitting this data while maintaining patients' privacy. EHRs should be released only with the patient's permission or within the confines of law, and any information released in the context of a clinical interaction is considered confidential and must be protected^(ii). ^(i) Atchinson, Brian K.; Fox, Daniel M. (May-June 1997). “The Politics of The Health Insurance Portability and Accountability Act” (PDF). Health Affairs. 16 (3): 146-150. doi:10.1377/hlthaff.16.3.146.^(ii) Rinehart-Thompson L A, Harman L B. Privacy and confidentiality. In: Harman L B, editor. Ethical Challenges in the Management of Health Information. 2nd ed Sudbury, Mass.: Jones and Bartlett: 2006. p. 53.

Healthcare facilities require access to this data if EHRs are to function as intended, and the key to preserving their confidentiality is to allow only authorized individuals to access this data. This requires that any relevant parties be pre-authorized to access the information based on established role-based privileges. Any user given access will be held accountable for use and misuse of the information they view, so properly assigning and validating user privileges comprises a major aspect of medical record securityi^(iii). ^(iii) American Health Information Management Association. The 10 security domains (updated) J Am Health Inf Management Assoc. 2012; 83:50.

Maintaining secure records has proven a rising challenge in multiple domains as increasing amounts of consumer data have become available. A 2014 report on medical identify theft in the United States suggests that incidences of data breaches are rising, with 2.32 million victims reported in 2014, a 21.7% increase from the previous year^(iv). Cloud storage, encryption, and basic password protection are vital aspects of ensuring EHRs remain secure. However, a 2011 survey found 73% of physicians confessed to texting other physicians about their work, and many healthcare professionals regularly access or discuss these records from personal mobile devicesv. Modern devices are easily misplaced, stolen, or wrongly accessed, so modern EHR transmission and storage protocols must highlight the use of encryption and proper validation. ^(iv) Ponemon Institute LLC. Fifth annual study on medical identity theft. Sponsored by the Medical Identity Fraud Alliance with support from: Kaiser Permanente, ID Experts, Experian Data Breach Resolution and Identity Finder, LLC. Traverse City (MI): Ponemon Institute LLC; 2015 February. 38 p^(v) HHS steps up HIPAA audits. Greene AHJ AHIMA. 2011 October; 82(10):58-9

Likewise, because medical records play crucial roles in informing treatment, steps must be taken to ensure that EHRs are accurate and unchanged following transmission. Loss or destruction of data during transfer will raise concerns about the usability of data, making them unfit as a basis for making care decisionsvi. Alterations to a patient's medical records may cause them to be billed for services they did not receive, misinform their caretakers, or lead them to receive unnecessary or dangerous treatments. ^(vi) North Carolina Healthcare Information and Communications Alliance, Inc. The benefits and risks of electronic health records

As can be seen, there is a need for a generalized and globally accessible system and method for (1) identifying a potentially unresponsive patient in an emergency setting, (2) locating that patient's EHRs in an unstandardized, byzantine record system, and (3) securely transmitting HIPAA-protected records from the EHR provider to the first responder at the site of treatment. improving the identification of a casualty at an injury or incident site, or on presenting at an Emergency services health care facility on an initial encounter with that facility.

SUMMARY OF THE INVENTION

In some aspects of the invention, a system for automatically determining the existence of an electronic health record corresponding to an identified casualty across one or more electronic health records (EHR) providers is disclosed. The system includes a server hosting a casualty identification and EHR matching service. The server includes a patient identification module configured to identify a casualty based on an identification of the casualty received from a mobile computing device operated by an emergency medical services (EMS) provider. A recognized patient messaging system (RPMS) is configured to query one or more electronic health records (EHR) service providers for the existence of a corresponding EHR belonging to the identified casualty upon receipt of the identification.

The Recognized Patient Messaging System (RPMS) protocol utilizes webhooks that upon receipt of the identification, deliver data to initiate a query, or a request, to a server of the one or more EHR service providers.

A database repository contains a plurality of EHR records. The database repository is affiliated with the one or more EHR service providers. Responsive to the one or more webhooks, the one or more servers of the EHR service providers initiate a query of the database repository to determine the existence the corresponding EHR. The one or more webhooks include a patient identifier corresponding to the identified casualty.

An application program interface (API) on the server hosting the casualty identification and EHR matching service is configured to receive a POST request from the server of the one or more EHR service providers. The POST request provides an indication of the existence of the corresponding EHR. When a corresponding EHR exists, the POST request provides information to request the corresponding EHR from a custodian of the EHR. When a corresponding EHR does not exist, the POST request returns a null result.

Other aspects of the invention include a computer program product stored on a non-transitory computer storage medium comprising machine-readable program code for causing, when executed, a computer to perform process steps. The process steps include receiving an identification of a casualty, at a first server hosting a casualty identification and electronic health record (EHR) matching service. Responsive to receiving the identification, the first server automatically queries a second server hosted by one or more electronic health record (EHR) service providers to determine the existence of a corresponding EHR matching the casualty.

The automatic query may include generating one or more webhooks by the first server upon receipt of the identification. The one or more webhooks are distributed to the second server and include a user defined callback to communicate one or more of a push notification, a query, or a request, to the second server to determine the existence of the corresponding EHR. The webhook notifies a webhook listening service, set up by the EHR to query their respective databases to determine the existence the corresponding EHR.

The process steps may also include, the EHR service sending a POST request corresponding to the first server's application program interface (API) endpoint. The POST request provides an indication of the existence of the corresponding EHR. When a corresponding EHR exists, the POST request includes relevant contact information to request the corresponding EHR from a custodian of the EHR. When a corresponding EHR does not exist, the POST request returns a null result.

Yet other aspects of the invention include a method of automatically matching an electronic health record (EHR) to an identified casualty. The method includes receiving an identification of a casualty at a first server hosting a casualty identification and electronic health record (EHR) matching service. Upon receipt of the identification, a second server hosted by one or more electronic health record (EHR) service providers are automatically queried to determine the existence of a corresponding EHR matching the casualty. When the corresponding EHR is located, the method automatically transmits a notification of the existence of the corresponding EHR to a mobile computing device of a medical provider treating the casualty.

In some embodiments, the step of automatically querying includes distributing one or more webhooks by the first server upon receipt of the identification. Via the webhook, the information is transmitted to the second server. The webhook broadcasts comprising a user defined callback to communicate one or more of a push notification, a query, or a request, to the second server to determine the existence of the corresponding EHR. Responsive to receipt of the one or more webhooks, a database repository affiliated with the one or more EHR service providers is automatically queried to determine the existence the corresponding EHR.

In some embodiments of the method, a POST request is received at an application program interface (API) of the first server from the second server. The POST request providing an indication of the existence of the corresponding EHR. When a corresponding EHR exists, the POST request provides contact information to request the corresponding EHR from a custodian of the EHR. When the corresponding EHR does not exist, the POST request returns a null result.

These and other features, aspects and advantages of the present invention will become better understood with reference to the following drawings, description and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a representative system architecture for the ERInfo platform.

FIG. 2 illustrates trust relationships of the ERInfo platform.

FIG. 3 illustrates participating parties in the exchange of patient information within the ERInfo platform.

FIG. 4 illustrates trust exchanges within the ERInfo platform via smart contracts.

FIG. 5 illustrates a representation of a flow of trust within the ERInfo platform.

FIG. 6 illustrates a recognized patient EHR query provided through the ERinfo platform.

FIG. 7 illustrates delivery of an EHR to the requesting provider.

FIG. 8 illustrates a diagram illustrating implementation of a Recognized Patient Messaging System (RPMS) protocol.

FIG. 9 illustrates a timing and sequencing of the RPMS protocol.

FIG. 10 illustrates a user interface for obtaining an identity of a casualty from a facial recognition module.

FIG. 11 illustrates a schematic diagram for a representative use of the RPMS to obtain a casualty EHR information.

DETAILED DESCRIPTION OF THE INVENTION

The following detailed description is of the best currently contemplated modes of carrying out exemplary embodiments of the invention. The description is not to be taken in a limiting sense, but is made merely for the purpose of illustrating the general principles of the invention, since the scope of the invention is best defined by the appended claims.

Broadly, embodiments of the present invention, hereinafter ERinfo, provides an improved platform with the ability to determine the existence of an EHR from one or more cooperating EHR service providers to determine the availability of an EHR for an identified patient. If relevant EHRs are found, the EHR provider can return a response indicating the location of the EHR.

As seen in reference to FIG. 1 , the ERinfo platform 10 may include three integral modules as part of the trust pathway, each addressing one of the needs in secure EHR access: (1) a patient identification module 20, which may include a facial recognition module, (2) a recognized patient messaging system (RPMS) 40, and (3) a blockchain trusted identification module 60. The three modules acting in concert may allow near-instantaneous and secure access to the casualty's protected health information from the authorized medical provider's smart phone 13, or other mobile computing device.

Once a casualty's identity has been determined, the ERinfo's platform 10 may provide healthcare professionals 14 with an indication of the existence of EHRs 15 maintained by one or more EHR providers 16, allowing access to vital records on site. First responders and emergency physicians 14 will be able to begin targeted treatment and contact relevant individuals and providers significantly faster, lessening unnecessary diagnostic tests and expenses while facilitating vital EHR 15 communication. The platform 10 addresses the challenge of matching an identified patient with an existing EHR 15 that may be kept by one or more EHR providers 16.

The ERinfo platform 10 provides a timely and secure system applicable to many contingencies, including but not limited to: a) patients who are disoriented or unresponsive due to trauma or medical emergency; b) Individuals non-compliant due to alcohol or drug overuse; c) “Silver Alerts” when patients with Alzheimer's or dementia become lost or disoriented; d) Natural disasters & mass casualties, in which high volumes of patients must be identified under high-stress, chaotic circumstances; and d) patients with low medical literacy regarding their healthcare background and risk factors.

As seen in reference to FIG. 1 , once a patient 12 has been identified, the recognized patient messaging system (RPMS) 40 will push queries to one or more cooperating EHR service providers 16 ₁-16 _(n) to determine the availability of an EHR 15 for the identified patient 12. If relevant EHRs 15 are found, the EHR provider 16 ₁-16 _(n) will return a response indicating the location of the EHR records 15. If relevant EHRs 15 are not found, the system 10 notifies the first responder 14 of the absence of an existing EHR so that time is not spent waiting on a result that will not be forthcoming.

The recognized patient messaging system 40 (RPMS) is responsible for the determination of the existence of and a location of a recognized patient's medical records 15. Once a patient has been identified by the presenting image or any other identification means, the RPMS 40 will push a query to one or more EHR providers 16 in order to determine which EHR provider 16 ₁-16 _(n) may have the identified patient's records in their system. The query may be based on relevant patient demographic information that may be captured during the matching of the presenting image to the source providing the matching identity for the patient, or patient demographic information obtained from the patient, and one or more other sources. By way of non-limiting example, the query may include: First Name, Last Name, Address, SSN, a Medical Health Insurance number, a Medical Health Record number, Date of birth, etc.

If one of the EHR providers 16 ₁-16 _(n) identifies the patient's information in their system, through one or more of their participating hospitals 18, healthcare providers, clinics, and the like, they will return a response to the RPMS 40 indicating that one or more EHR records 15 are available for the identified patient 12.

The RPMS 40 connects ERinfo in real time to the various EHR providers 16 ₁-16 _(n). In some embodiments, the one or more EHR providers 16 ₁-16 _(n) may implement a listening module configured to autonomously receive the RPMS 40 push notifications.

ERinfo 10 runs a service or services on its servers that broadcast the query containing the patient's identifying information matched to any and all EHR providers 16 ₁-16 _(n) that are running a listening service that may be implemented using ERInfo's RPMS software development kit and proprietary APIs for the one or more EHR providers 16. In the alternative, should a third party listener be made available that can accept broadcast messages from ERinfo's RPMS 40, the third party listener can be used as well by the one or more EHR providers 16 ₁-16 _(n).

The ERinfo listening service running on the one or more EHR provider 16 ₁-16 _(n) servers may also configured to transmit a response from the one or more EHR providers 16 ₁-16 _(n) that are responding to the query for the existence of a corresponding EHR 15 for the patient 12 within their system. When the ERinfo platform 10 receives a response, the system may be configured to transmit the existence and location of the patient's EHR 15 to the medical provider 14.

In a preferred embodiment, communication between the RPMS 40 and EHR companies 16 ₁-16 _(n) is executed utilizing an ERinfo Recognized Patient Messaging System (RPMS) protocol 42. The RPMS protocol 42 takes advantage of one or more webhooks 44—user defined HTTP callbacks that send out push notifications, queries, or requests via HTTP POST requests upon predetermined mutations and occurrences, such as receipt of the patient identification. As seen in reference to FIGS. 8 and 9 , utilizing these in combination with one or more API calls, the ERinfo RPMS 45 protocol is executed as follows:

Upon recognition of a patient 12, whether through the facial recognition query, or otherwise, an ERinfo RPMS webhook trigger 45 is issued, announcing the request for the identified patient's information. The webhook 44 transmits a patient identifier 46. The one or more participating EHR companies 16 ₁-16 _(n) following the ERinfo RPMS protocol 42 will be notified of the new query. The one or more participating EHR companies 16 ₁-16 _(n) will execute an internal query of their database 17 to determine if the identified patient 12 is present in their system. The internal query will check for the existence of patient records 15 in the one or more hospitals or providers 18 _(n) utilizing their EHR system 16 _(n). If an EHR 15 corresponding to the identified patient 12 is found, the EHR company 16 _(n) servers will execute an HTTP POST request 46 to an ERinfo API containing relevant information pertaining to the existence of thee record and contact information to obtain that record 15. If an EHR 15 is not found, the HTTP Post request 46 return null result.

As seen in reference to FIG. 9 , a timeline of the ERinfo RPMS protocol 42 and its location in the ERinfo identification protocol 40 is demonstrated in FIG. 3 . The ERinfo RPMS webhook 44 may be distributed to the one or more participating EHR companies 16 ₁-16 _(n) and integrated into their respective servers and systems accordingly.

Upon determining a casualty identity, a webhook trigger 45 is issued by the ERInfo server 10 to the one or more EHR companies 16 ₁-16 _(n). The webhook trigger 45 includes one or more patient identifiers 46. Responsive to the trigger 45, the one or more EHR companies 16 ₁-16 _(n) execute a query of the database 17 of their participating healthcare providers 18 for one or more EHR records 15 corresponding to the one or more patient identifiers 46.

Upon completion of the query, the servers of the one or more EHR companies 16 ₁-16 _(n) transmit a response to ERInfo 10. A return POST request 48 will contain a record locator 47 including the generic contact information, e.g. phone number to call in order, for a custodian of the EHR 15, that will allow the first responder 14 to request access to the EHR 15. In this instance, while the medical provider 14 has awareness of the existence and location of the patient's corresponding EHR 15, a direct link to the patient's corresponding EHR is not provided, and the record 15 may be retrieved utilizing conventional means, in a protected manner.

As will be appreciated, the RPMS protocol 42 doesn't convey protected health information, rather it provides the medical provider 14 awareness of the existence of the corresponding EHR for the patient 12. The record locators 47 allow the medical provider 14 the ability to contact the record custodian and obtain the relevant EHR 15.

In the event the medical provider 14, patient 12, and EHR provider 16 are all participants of the same private ledger blockchain trust, the ERinfo platform 10 provides for the EHR provider 16 to forward authentication and access credentials to the medical provider 14 so that the medical provider 14 can directly access the patient's protected health information 15 that is resident on one or more of the EHR provider's systems 16 via a blockchain trusted identification module (BTIM) 60.

The BTIM 60 establishes a consensus and a trustworthiness of the EHR provider 16 ₁-16 _(n) and the first responder 14, ensuring secure transfer of EHR documents 15 directly to the first responder 14 via the trust pathway 62. Once complete, the three modules acting in concert will allow near-instantaneous and secure access of protected information from the authorized medical provider's phone.

The Trust Pathway 62 addresses the two major hurdles to obtaining vital EHRs 15 in emergency situations by employing innovative models within the central ERinfo platform 10: Messaging via the recognized patient messaging system 40, and EHR 15 delivery through the BTIM 60. The modules may be operated sequentially to authorize secure transmission of EHRs. 15.

When the RPMS 40 receives the notification, the blockchain trusted identification module (BTIM) 60 is responsible for establishing the secure retrieval of HIPAA-protected information using a blockchain enabled trust pathway 62. As seen in reference to FIG. 3 , all parties involved, including first responders 14, EHR service providers 16, and patients 12 who have opted into ERInfo functionality, will execute a smart contract with ERInfo 10 establishing a consensus on accessibility and sharing of the EHR 15 and other vital patient information. For an enrolled patient 12, as seen in reference to FIG. 4 , because the patient 12 has signed a smart contract to establish a trust pathway with ERInfo 10, and ERInfo 10 has created a smart contract with the one or more EHR providers 16, the patient's EHR 15 can be released to the requesting provider 14 at the site of treatment.

In the case of a non-enrolled patient 12, when the provider 14 verifies an emergency condition exemption, a trust pathway 62 with ERInfo 10 and the EHR provider 10 is executed, as illustrated in reference to FIG. 5 , enabling the release of the one or more EHRs to the requesting provider 14. In either case, the trusted pathway 62 is configured so that the patients one or more EHRs 15 are delivered directly to the requesting provider 14 so that the ERInfo platform 10 need not be HIPAA compliant.

Using the blockchain-protected system in which a plurality of participants are consensus providers ensures that no single party can serve as a vulnerable endpoint for accessing sensitive patient information; there must be consensus among all members of the decentralized ledger to verify a valid EHR 15 request. This ensures that only actively licensed (and authorized through ERInfo platform 10) providers 14 can access the system, and that a security breach of the ERInfo database 30 itself does not allow intruder access to HIPAA data of patients 12 who have opted in.

Once the patient has been recognized and their EHRs located, the blockchain trusted Identification module 60 validates and automatically executes the one or more smart contracts, thereby permitting the EHR provider 16 to deliver the identified patient's EHRs 15 to the first responder or medical provider 14. The one or more smart contracts may include a smart contract that a medical provider 14 enters into with ERinfo 10 when enrolling with ERinfo 10. The one or more smart contracts may also include a smart contract between ERinfo 10 and the one or more EHR providers 16. In turn, the EHR provider 16 may require an additional contract with each facility/organization 18 using its system, the additional contract may also be a smart contract. The one or more smart contracts may also include a smart contract between the patient 12 and ERinfo 10.

The ERinfo platform 10 uses a distributed application (DApp) to establish transitive trust through enrollment with the system 10. The DApp manages separate enrollment for the patient 12, the medical provider 14, and the EHR service provider 16 through one or more smart contracts: When an EHR service provider 16 is enrolled, the one or more smart contracts on a blockchain system, when executed, will provide previously unauthorized first responders 14 to seamless access to the patient's EHR information 15 by the EHR service provider 16. The ERinfo platform 10 creates transitive trust with the DApp managing enrollment, the Patient's smart contract for a record release can be automatically executed using ERInfo's established trust across all parties. Trust can be then be established between the EHR provider 16 and the medical provider 14. The EHR provider 16 can then provide access to the patient's record 15 with trust and release the relevant information.

Patient Enrollment. When a patient 12 enrolls with ERInfo 10, the patient 12 can provide ERinfo 10 with appropriate and legally acceptable permission, a smart contract, to retrieve their (HIPAA) protected medical information 15. With the patient's smart contract on the blockchain, previously unauthorized first responders 14 are granted access to the patient's information 15 in the event of an emergency and execution of the patient's smart contract.

The “trust” relationship is created by ERinfo 10, where the patient 12 can rely on ERinfo 10 to ensure that only properly authorized medical professionals 14 and first responders 14 can access their information, and that institutions 16, 18 that are part of ERInfo's blockchain can publish that information 15 to those digitally authenticated medical providers 14.

Medical Provider Enrollment. When a medical provider 14 enrolls as an ERinfo provider, ERinfo 10 validates the enrollment using credentialing services to ensure the user holds an active professional license. User validation may be provided via knowledge-based authentication (KBA) or other authentication methodologies.

Thus, ERinfo 10 provides a blockchain-enabled Trust Pathway 62 authorizing the exchange of HIPAA-protected records 15. Because authorization will depend on the addition of new transactions to a distributed ledger, implementation of the system architecture is based on an established consensus between the parties involved in the transactions. This consensus can be established by a system of transitive trust conducted through members enrolled in the ERinfo service 10.

The system of the present invention may include at least one computer with a user interface. The computer may include any computer including, but not limited to, a desktop, laptop, and smart device, such as, a tablet and smart phone. The computer includes a program product including a machine-readable program code for causing, when executed, the computer to perform steps. The program product may include software which may either be loaded onto the computer or accessed by the computer. The loaded software may include an application on a smart device. The software may be accessed by the computer using a web browser. The computer may access the software via the web browser using the internet, extranet, intranet, host server, internet cloud and the like.

The computer-based data processing system and method described above is for purposes of example only, and may be implemented in any type of computer system or programming or processing environment, or in a computer program, alone or in conjunction with hardware. The present invention may also be implemented in software stored on a non-transitory computer-readable medium and executed as a computer program on a general purpose or special purpose computer. For clarity, only those aspects of the system germane to the invention are described, and product details well known in the art are omitted. For the same reason, the computer hardware is not described in further detail. It should thus be understood that the invention is not limited to any specific computer language, program, or computer. It is further contemplated that the present invention may be run on a stand-alone computer system, or may be run from a server computer system that can be accessed by a plurality of client computer systems interconnected over an intranet network, or that is accessible to clients over the Internet. In addition, many embodiments of the present invention have application to a wide range of industries. To the extent the present application discloses a system, the method implemented by that system, as well as software stored on a computer-readable medium and executed as a computer program to perform the method on a general purpose or special purpose computer, are within the scope of the present invention. Further, to the extent the present application discloses a method, a system of apparatuses configured to implement the method are within the scope of the present invention.

It should be understood, of course, that the foregoing relates to exemplary embodiments of the invention and that modifications may be made without departing from the spirit and scope of the invention as set forth in the following claims. 

What is claimed is:
 1. A system for automatically determining an existence of an electronic health record corresponding to an identified casualty across one or more electronic health records (EHR) providers, comprising: a server hosting a casualty identification and EHR matching service, the server comprising: a patient identification module configured to identify a casualty based on an identification of the casualty received from a mobile computing device operated by an emergency medical service (EMS) provider; a recognized patient messaging system (RPMS) configured to query one or more electronic health records (EHR) service providers for the existence of a corresponding EHR belonging to the identified casualty upon receipt of the identification; and a blockchain trusted identification module (BTIM) configured to establish a consensus between the identified casualty, the one or more EHR service providers, and the EMS provider.
 2. The system of claim 1, wherein the consensus comprises: a first blockchain trust contract between the identified casualty and the casualty identification and EHR matching service; and a second blockchain trust contract between the one or more EHR service providers and the casualty identification and EHR matching service.
 3. The system of claim 2, further comprising: a blockchain enabled trust pathway established directly between the one or more EHR service providers and the mobile computing device of the EMS provider when the consensus of the identified casualty, the one or more EHR service providers, and the EMS provider are established.
 4. The system of claim 3, wherein the blockchain enabled trust pathway is configured to transmit the corresponding EHR from the one or more EHR service providers to the mobile computing device of the EMS provider.
 5. The system of claim 1, wherein the consensus comprises: an emergency condition exemption received from the EMS provider.
 6. The system of claim 5, further comprising: a blockchain enabled trust pathway established between the EHR service provider, the casualty identification and EHR matching service, and the mobile computing device of the EMS provider.
 7. The system of claim 6, wherein the blockchain enabled trust pathway is configured to transmit the corresponding EHR from the one or more EHR service providers to the mobile computing device of the EMS provider.
 8. The system of claim 1, wherein the RPMS is configured to utilize a webhook, that, upon receipt of the identification, pushes a notification to the one or more EHR service providers, broadcasting a user defined callback to communicate one or more of a push notification, a query, or a request, to a server of the one or more EHR service providers.
 9. The system of claim 8, further comprising: a database repository containing a plurality of EHR records, the database repository affiliated with the one or more EHR service providers; and responsive to the webhook, the one or more servers of the EHR service providers initiate a query of the database repository to determine the existence the corresponding EHR.
 10. The system of claim 9, wherein the webhook broadcasts a patient identifier corresponding to the identified casualty.
 11. The system of claim 1, further comprising: an application program interface (API) on the server hosting the casualty identification and EHR matching service configured to receive a POST request from the server of the one or more EHR service providers, the POST request providing an indication of the existence of the corresponding EHR, wherein when a corresponding EHR exists, the POST request provides information to request the corresponding EHR from a custodian of the EHR; and when a corresponding EHR does not exist, the POST request returns a null result.
 12. A computer program product stored on a non-transitory computer storage medium comprising machine-readable program code for causing, when executed, a computer to perform the following process steps: receiving an identification of a casualty, at a first server hosting a casualty identification and electronic health record (EHR) matching service; automatically querying a second server hosted by one or more electronic health record (EHR) service providers to determine an existence of a corresponding EHR matching the casualty; and determining, via a blockchain trusted identification module (BTIM), a consensus between the casualty, an emergency medical services (EMS) provider, and the one or more EHR service providers.
 13. The computer program product of claim 12, the process steps further comprising: establishing a blockchain enabled trust pathway between the one or more EHR service providers and the EMS provider when the consensus is established.
 14. The computer program product of claim 13, the process steps further comprising: transmitting the corresponding EHR from the one or more EHR service providers to the EMS provider via the blockchain enabled trust pathway.
 15. The computer program product of claim 14, the process steps further comprising: when the consensus comprises: a first blockchain trust contract between the casualty and the casualty identification and EHR matching service; and a second blockchain trust contract between the one or more EHR service providers and the casualty identification and EHR matching service; establishing the blockchain enabled trust pathway directly between the EHR service provider and the EMS provider; and when the consensus comprises: an emergency condition exemption received from the EMS provider, establishing the blockchain enabled trust pathway between the EHR service provider, the casualty identification and EHR matching service, and the EMS provider.
 16. A method of automatically matching an electronic health record (EHR) to an identified casualty, comprising: receiving an identification of a casualty, at a first server hosting a casualty identification and electronic health record (EHR) matching service; automatically querying a second server hosted by one or more electronic health record (EHR) service providers to determine an existence of a corresponding EHR matching the casualty; and determining, via a blockchain trusted identification module (BTIM), a consensus between the casualty, an emergency medical services (EMS) provider, and the one or more EHR service providers.
 17. The method of claim 16, the process steps further comprising: establishing a blockchain enabled trust pathway between the one or more EHR service providers and a mobile computing device of the EMS provider when the consensus is established.
 18. The method of claim 17, further comprising: transmitting the corresponding EHR from the one or more EHR service providers to the mobile computing device of the EMS provider via the blockchain enabled trust pathway.
 19. The method of claim 17, the process steps further comprising: when the consensus comprises: a first blockchain trust contract between the casualty and the casualty identification and EHR matching service; and a second blockchain trust contract between the one or more EHR service providers and the casualty identification and EHR matching service; establishing the blockchain enabled trust pathway directly between the EHR service provider and the EMS provider; and when the consensus comprises: an emergency condition exemption received from the EMS provider, establishing the blockchain enabled trust pathway between the EHR service provider, the casualty identification and EHR matching service, and the mobile computing device of the EMS provider. 